Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Don't assign a default project path for package specs that don't have a fixtures directory #15990

Merged
merged 1 commit into from Oct 25, 2017

Conversation

nathansobo
Copy link
Contributor

References atom/spell-check#223, but it won't fix it until this PR is hotfixed to stable.

This prevents package specs that don't have a fixtures directory from attempting to read files out of a non-existent directory inside the ASAR bundle, which causes ENOTDIR errors in superstring.

If the spec does not have a parent folder containing a fixtures directory, we now set the default project path to os.tmpdir().

This prevents package specs that don't have a fixtures directory from
attempting to read files out of a non-existent directory inside the ASAR
bundle, which causes ENOTDIR errors in superstring.

If the spec does not have a parent folder containing a fixtures
directory, we now set the default project path to `os.tmpdir()`.
@nathansobo nathansobo merged commit d44d6ab into master Oct 25, 2017
@nathansobo nathansobo deleted the non-asar-legacy-spec-project-path branch October 25, 2017 18:57
nathansobo pushed a commit that referenced this pull request Oct 25, 2017
Don't assign a default project path for package specs that
nathansobo pushed a commit that referenced this pull request Oct 25, 2017
Don't assign a default project path for package specs that
@iolsen iolsen changed the title Don't assign a default project path for package specs that Don't assign a default project path for package specs that don't have a fixtures directory Oct 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant